Skip to content

Fix XMLHttpRequest.setRequestHeader to append duplicate headers per spec#56394

Open
zmunm wants to merge 2 commits intofacebook:mainfrom
zmunm:xhr-setrequestheader-append
Open

Fix XMLHttpRequest.setRequestHeader to append duplicate headers per spec#56394
zmunm wants to merge 2 commits intofacebook:mainfrom
zmunm:xhr-setrequestheader-append

Conversation

@zmunm
Copy link
Copy Markdown

@zmunm zmunm commented Apr 9, 2026

Summary:

XMLHttpRequest.setRequestHeader() overwrites the previous value when called multiple times with the same header name. Per the XHR Living Standard §4.5.2, duplicate headers should be appended with , .

Real-world example: Sentry JS SDK assumes append behavior
when setting the baggage header, which causes previously set baggage values to be silently dropped on React Native.

Changelog:

[GENERAL] [FIXED] - Fix XMLHttpRequest.setRequestHeader to append duplicate headers per spec

Note: This is technically a breaking change for code that relied on the previous overwrite behavior (e.g., calling setRequestHeader twice to replace a value). However, that behavior was non-compliant with the XHR spec, so such code should use a single call with the desired final value instead.

Test Plan:

Unit tests — 3 tests added in XMLHttpRequest-test.js:

  • Appends values when same header is set twice
  • Merges case-insensitively
  • Throws when called before open()

Run the snippet below in both browser DevTools and RN debugger console to compare:

const xhr = new XMLHttpRequest();
xhr.open('GET', 'https://httpbin.org/headers');
xhr.setRequestHeader('X-Test', 'value1');
xhr.setRequestHeader('X-Test', 'value2');
xhr.onload = () => {
  const headers = JSON.parse(xhr.responseText).headers;
  console.log('X-Test:', headers['X-Test']);
  // Before: "value2"
  // After:  "value1, value2"
};
xhr.send();

zmunm added 2 commits April 9, 2026 16:37
Add tests verifying XHR spec compliance for setRequestHeader:
- Same header called multiple times should append with ', '
- Case-insensitive header name merging
- Throw when called before open()

These tests currently FAIL, exposing the spec violation.
Comply with XHR Living Standard 4.5.2: when setRequestHeader is
called multiple times with the same header, append with ', '
instead of overwriting.
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 9, 2026

Hi @zmunm!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 9, 2026
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 9, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-tools facebook-github-tools bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Apr 9, 2026
@meta-codesync
Copy link
Copy Markdown

meta-codesync bot commented Apr 9, 2026

@fabriziocucci has imported this pull request. If you are a Meta employee, you can view this in D100144689.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant